error return in a sentence

1. changed the API so maxlag errors return with an HTTP status code 503 ( where formerly they returned with a 200 and an API error message ).
2. Secondly, yes it is almost always wrong to use eof ( ) in perl ( the read operators have eof / error return values which you should be checking for instead ).
3. The problem is, you'll have to deallocate the memory when you're done, something you're likely to forget ( especially if there is an error return before the program line where you deallocate the memory ), thereby getting a memory leak.
4. HRESULTS were originally defined in the IBM / Microsoft OS / 2 operating system as a general purpose error return code, and subsequently adopted in Windows NT . Microsoft Visual Basic substantially enhanced the HRESULT error reporting mechanisms, by associating an IErrorInfo object with an HRESULT error code, by storing a pointer to an IErrorInfo COM object in thread-local storage.
5. After initially omitting exceptions, the exception-like / mechanism was eventually added to the language, which the Go authors advise using for unrecoverable errors such as those that should halt an entire program or server request, or as a shortcut to propagate errors up the stack within a package ( but not across package boundaries; there, error returns are the standard API ).
6. It's difficult to find error return in a sentence.